Skip to main content

EPA Region 5 State Mapping Projects ↔ RSMS mapping

Standalone reference: how patterns described in the EPA Region 5 State Mapping Projects Quick Start Guide (2024) relate to RSMS implementation choices.

Source in-repo: text extract at docs/rsms-upgrade/r5-state-mapping-projects-quick-start-guide-2024-extract.txt (extracted from PDF; layout/OCR artifacts possible).

Cross-links: rsms-threat-layers-overview (scope & rollout), rsms-threat-layers-backlog (prioritized backlog IDs), rsms-task4-and-r5-layer-catalog (Task 4 checklist + full R5 layer enumeration with links/status).


Program intent vs RSMS intent

R5 mapping programRSMS analogue
Situational awareness for OSCs; downstream/upwind vulnerabilities; upstream PRPsPlanning & scenario context: show plausible upstream infrastructure and regulated facilities adjacent to modeled reaches without changing plume physics
MFA-governed response.epa.gov access; Government vs Stakeholder layer mixesRSMS ships public or APTIM-licensed subsets; no requirement to reproduce EPA portal auth in-app for MVP overlays
Rich widget set (trace downstream, ER widgets, reporting)MVP focuses on GeoJSONLayer / FeatureLayer overlays + pop-ups; defer parity with EPA widgets unless product asks

Layer catalog patterns → RSMS hook

R5 pattern / layer theme (guide)Typical upstream source familiesRSMS hook (near-term)
Facility Registry Service (FRS) and FRS-derived ESF-10 style groupings (mentions ICIS, NPDES, RCRA themes in guide)EPA FRS API / snapshots; NCSDownload where batch neededCurated point GeoJSON per RSMS corridor + attributes trimmed for pop-ups; optional rsms_reach_key / mile bucket columns
USGS NWIS streamgagesUSGS NWIS (waterservices, mapper exports); complements NOAA AHPS-style layers in the guidePilot A: port legacy RSMS gage overlay into Maps SDK (GeoJSONLayer / features); context-only unless separately wired to forcing
Pipeline crossing points & spill projectionsEPA-derived crossing analytics (guide ties to NHD intersections); operator GIS where licensedShip crossing points after Pilot B backlog wave; spill projection linework later (heavier QA)
Railroad crossing points & spill projectionsSame pattern as pipelines in guideSame staged approach
ISA / sensitivity-style overlays (guide references inland sensitivity atlas themes in reporting workflows)Federal/state bundled layersRSMS may ship subset near Ohio modeled extents only
NPDES outfalls / discharge themesFRS NPDES facets; state WQS/permit GISStrong backlog candidate (rsms-threat-layers-backlog.md L01) after pilots A/B
Drinking water / intakes (guide mentions water infrastructure classes in overview)State health/environmental GIS; federal DW datasets where applicableUseful downstream context; watch attribution/licensing
Vulnerable populations / facilities (schools, hospitals, etc.—overview text)Census / NCES / HIFLD-style open dataSecondary backlog—privacy/sensitivity varies; prefer aggregated or public datasets

Tool / workflow patterns → RSMS stance

R5 capabilityRSMS MVP stanceLater optional
Trace Downstream (hydro tracing widget)RSMS already centers on river geometry + mile axis from model domain; do not duplicate EPA trace unless product merges hydraulic domain with national hydro graphPossible future: link-out or lightweight trace only if shared hydro IDs stabilize
Search Location / Find AddressUse existing map/search widgets if already mounted; otherwise deferESRI geocoder integration
Reporting tools (PDF vulnerable populations, pipe/rail crossing filters, Crossing ID filters—guide)Out of MVP for RSMS overlaysCould inspire export CSV/PDF of visible upstream features
Weather radar widgetsNot Task 4 coreSeparate product decision

Practical takeaway

RSMS ships Pilot A — USGS streamgages then Pilot B — USACE bridges (see rsms-threat-layers-overview.md / rsms-threat-layers-backlog.md L00, L08). Use the R5 guide as a menu for additional regulatory/threat themes afterward—not as a mandate to replicate EPA’s portal.


Document history

DateChange
2026-05-22Pilots locked to USGS gages + USACE bridges; NPDES moved to post-pilot backlog.